home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
By Popular Request 2.0
/
By Popular Request 2.0 (Arsenal Computer).ISO
/
amiga_1
/
adsinfo.lha
/
ADSPOL-1.004
< prev
next >
Wrap
Text File
|
1994-04-14
|
35KB
|
855 lines
AMIGA DISTRIBUTION SYSTEM
(PRELIMINARY RELEASE)
Original Dated: April 6, 1990
Current Revision Date: Apr 15, 1994
Version: 1.xxx
_______________________________________________________________
PURPOSE and INTRODUCTION
_______________________________________________________________
o What is ADS?
- ADS is an acronym for Amiga Distribution System and
represents:
- The OFFICIAL Amiga Software Distribution System.
- The OFFICIAL Non-Backbone Amiga ECHOmail Distribution System.
o The purpose?
- To provide a means of distributing and announcing
the release of Amiga Public Domain (PD)/Shareware/Freeware
Programs/Files, that are not normally distributable
through the SDS, to nodes interested in Amiga only
files.
- To provide a means of distributing Non-Backbone Amiga Related
ECHOmail Message Areas.
o General concept?
ADS Message Echos
- These are messages areas carried by the ADS Network. They
are in the same transmission format as the Fidonet EchoMail
standard.
ADS File Echos
- 'File echos' are not to be confused with 'message echos'.
They are FILES classed under different categories or 'AREAS'
which are defined in your TICK configuration.
- Files will be distributed using the TICK format software such
as ...
(Amiga Software)
StarTick [v2.40] Chris Adams (1:308/80) --- Star-Net
MyTick [v2.05] Chris Adams (1:308/80) --- MEBBS-Net
AmigaTick [v0.75] Russel Miranda --- Paragon
XTick [v0.61] Magnus Lilja --- XenoLink
Ftick --- Foozle
Pdqtick Steve Lewis (1:114/52) --- DLG
(MS-DOS Software)
TICK [v2.10 ] Barry Geller (1:266/12) --- IBM
-*Note*- Beta software is not to be used without first notifying
your Zone Coordinator and the Zone 1 Coordinator in case a problem
should develop, problems can be resolved quicker.
-*Note*- In the case of Beta Software interfering with the smooth
operation of ADS. You will have three choices.
1) Go back to a known working Beta Version.
2) Run released software.
3) Failure to comply with one of the above will mean your removal
from ADS.
o ADS Administration Board
Purpose: To Organize, coordinate, and enforce the policies of ADS.
All disciplinary action will go through thr ADS Adm.
Board. The board will act as a "court of appeals" for
any person(s) in the ADS system with complaints. The ADS
Adm. board has the final say in all maters.
o ADS Distribution Organizational Structure
- The ADS Administration Board consists of the Zone
Coordinators.
o ADS Zone 1 Coordinator
-* As ADS was originated in Zone 1, All Control of ADS shall remain in Zone 1.
Purpose: To oversee the operation of ADS in Zone 1 and ADS as a whole.
General Concept: The Zone 1 Coordinator will work with all Zone
Coordinators to insure the smooth operation of ADS as a whole.
- Ensure that all zones are in compliance with this Policy.
- Act as a mediator for policy complaints between zones under the
guidance of the Administration Board.
- Implement administrative files as needed. (I.E. ADS Dhub apps,
hatching apps, site listings, etc...)
- Implement New File and Echo areas as they are needed.
The Zone 1 Coordinator may appoint a Zone Coordinator under the
the following conditions
- A new zone has applied for access to ADS International and that zone
has not elected or appointed a Zone Coordinator.
- A Zone Coordinator has been removed or quits his position. The Zone
1 Coordinator will appoint one to represent that zone until one
is appointed or an election can be held in that zone.
- If the ADS Adm. Board calls for the dismissal of the Zone 1
Coordinator, a new one will be appointed by the board.
Note: Zone 1 STARS included in Vote.
The Zone 1 Coordinator may choose to oversee or appoint a neutral party
to hold the election for a ZC in a zone.
- If the Zone 1 Coordinator decides to steps down, he may appoint his
successor upon the approval of the ADS Adm. Board.
o ADS Zone Coordinators
Purpose: To oversee the operation of ADS in the their Zones.
General Concept: Zone Coordinators will follow this Policy and
can incorporate their own Zone policies which cannot
conflict with this policy. This Policy will supersede
any Zone policy.
Each Zone will have a Zone Coordinator (ZC) that can either be
elected or appointed by their peers in their zone or appointed by
the Zone 1 Coordinator.
The ZC can distribute ADS in their Zone any way they see best as
long as they follow the guidelines within this policy. Any
changes within zones must meet the approval(s) of the ADS
Adm. Board.
Removal of Zone Coordinator (see above under Zone 1 Coordinator)
o ADS ZONE STARS
Purpose: Provide distribution of the ADS files and Non-backbone
echos to official ADS sites within their Zone and to
connect directly into a Zone 1 Star.
Scope: The Zone Stars should connect to a Zone 1 Star
of their Choice. Note: Only Zone Administrative echoes
will be carried by ADS Stars only. Therefore if you
choose not to connect directly to a Zone 1 Star for
whatever reason, your ZC must pick up the Coordinators
echo directly from a Star, it will not be distributed
any other way. More then one Zone Star is encouraged to
connect into Zone 1.
ZCs MUST carry the ADSSTAR echo, this echo is for ADS
Stars and ZCs ONLY.
o ADSSTARS
Purpose: Provide distribution of the ADS files and Non-backbone
echos to official ADS sites (Star, DHubs) and Zone Stars.
Scope: The ADSSTARS will all call each other at least
once a day to pick up ALL! ADS File and Echo Areas
available and provide a place for the ADS_DHUBS to pick
them up for Node distribution.
ADSSTARS MUST carry the ADSSTAR and ADS_COORD echoes.
ADS Stars Primary Function
-*Note*- All ADS Stars are Required to carry ALL ADS AREAS "Echo/File"
^^^ ^^^ ^^^^ ^^^^^^^ ^^^^ ^^^ ^^^ ^^^^^ ^^^^^^^^^
and Call their assigned Stars Once Daily "Stars call only Stars"
^^^^ ^^^^^ ^^^^ ^^^^^
Zone Stars are recommended to Call Daily but are required
to call a minimum of 3 non-consecutive days per week.
-*Note*- In Special cases a Multi-node Star may apply to his/her
ZC for Dhub Status or any other special needs that they may
feel they need.
- A typical Zone 1 Star layout would look like this with two Stars from
Zone's 2 3 connecting in at different stars.
This type of system now gives ADS a much more reliable system unlike
in the past, Everyone called one system. When that system went down
ADS was a total mess there was no backup's. Now if a star goes down
(s)he now only effects a few and a new link can be reestablished in a
much shorter time.
+-----------+ +-----------+ +-----------+ +-----------+
| ADS STARS | ------- | ADS STARS | | ADS STARS |- | ADS STARS |
+-----------+ +-----------+ +-----------+ +-----------+
| \ / Zone 3
| \ /
| \ /
| \ /
+-----------+ \+-----------+/ /+-----------+
| ADS STARS | | ADS STARS | / | ADS STARS |
+-----------+ +-----------+ / +-----------+
/ | \ /
/ | \ /
/ | \ /
/ | \ /
+-----------+ +-----------+ +-----------+
| ADS STARS | | ADS STARS | | ADS STARS |
+-----------+ +-----------+ +-----------+
| | |
+-----------+ +-----------+ +-----------+
| ADS STARS | | ADS STARS | | ADS STARS |
+-----------+ +-----------+ +-----------+
Zone 2 Zone3 Zone 2
-*Note*- It is also recommended that each Zone Have two Stars connect into
Zone 1.
ADS Stars Secondary Function
The second function of the ADS Star is to distribute Files/Echos to
the ADS DHubs "Distribution Hubs" and Feed his local Net and any Authorized
Hatching Nodes. If assigned a Zone Star (s)he will also feed that Star.
+------------+ +-----------+ +-----------+
| Local Node | | ADS DHUB | | ADS STAR |
+------------+ +-----------+ +-----------+
\ | / Zone 3
\ | /
\ | /
\ +-----------+
+-----------+ \| ADS STAR | +-----------+
| ADS STAR |---------- | |-------| ADS DHUB |
+-----------+ +-----------+ +-----------+
/ | \
/ | \
/ | \
/ | \
+-----------+ +-----------+ +------------+
| ADS DHUB | | ADS DHUB | | Local Node |
+-----------+ +-----------+ +------------+
- ADS DHUB'S "Distribution Hub" who's function is to distribute ADS
File/Echo Areas to end Node's and hatch new files and messages into
the ADS Network.
+------------+ +-----------+ +-----------+
| Local Node | | Node | | Node |
+------------+ +-----------+ +-----------+
\ | /
\ | /
\ | /
\ +-----------+
+------------+ \| ADS | +------------+
| Local Node |---------- | DHub |-------| Node |
+------------+ +-----------+ +------------+
/ | \
/ | \
/ | \
/ | \
+------------+ +------------+ +------------+
| Hatch Node | | Hatch Node | | Local Node |
+------------+ +------------+ +------------+
ADS DHUB(s)
-----------
Provides the connection between the ADSSTAR System/s and
the end users. They are also an authorized to HATCH site.
Scope: Only approved nodes by the ADS Zone Coordinator may become
an ADS DHub.
DHubs are to poll the Stars at least three times a week,
(not to be consecutive days), more would be preferred but
not required. All DHubs are required to carry any ADS area
that they have ACCESS too upon request from a node, but are
not required to carry them until such request is made.
DHubs will feed ONLY end nodes --* DHubs will not Feed
other DHubs or Star's other then their assigned Star *--
DHubs must hold all file releases for a minimum of thirty
(30) days after released. --* FILES must be made AVAILABLE
for file requesting and/or downloading during that Period *--
DHubs will have the responsibility to 'HATCH' new releases
into the system, as well as monitoring any hatch that may
come from a 'downstream' links.
o Official Language.
The official Language to be used for the ECHOmail areas
(ADS_ANNOUNCE, ADS_FIL_REL) *and* all files and descriptions
is ENGLISH. A program may have additional language versions
contained within the archive, but there MUST be an English version.
o Official ADS Packages & listings.
Scope : Instead of adding or updating ADS Policy every time an new area is
added or deleted the following packages will be updated and made
available by the ZC's to all Authorized ADS Distribution sites.
i.e (ZCs/Stars/DHubs)
File Name MagicName i.e File Req Description
------------------------------------------------------------------------
ADSINFO.LZH ADSINFO Contents
Adspolcy.xxx Current Policy
Adsapp.app Application to Join ADS
adsareas.lst list of Echo areas
adsfiles.lst list of File areas
adssyszx.lst list of ads sites
ADSHATCH.TMP Official Hatch template. Not to be File
Requestable. (available to Authorized
Sites only.)
ADSSYSZ1.LST ADSSITES listing of ads sites in each Zone.
ADSSYSZ2.LST ADSSITES (Magic Name gets all Zones)
ADSSYSZ3.LST ADSSITES
ADSAPP.APP ADSAPP application form for joining ADS
ADSAREAS.LST ADSAREAS Current list of ads message areas
ADSFILES.LST ADSFILES Current list of ads file areas
o Templates & Area Setup Examples.
-* Note these Templates listed below are for Referance Only and May not
be the same contained in the current ADSINFO package. These listings
may be change at any time with out modification of this Policy. *-
o (Amiga Distribution System Message Echos - ECHOmail examples)
TAGNAME DESCRIPTION
------- -----------------------------
ADS_COORD ADS Coordinator ONLY Echo
AMIGA_INFO Amiga Information
AMIGA_TALK General Amiga Chit Chat echo
All echomail will be treated as it is under current Fido-Net Policies.
Refer to ADSAREAS.lst for current listing.
o (Amiga Distribution System File Echos)
- These 'echos' are not like 'message echos'. Basically, they
are 'AREAS' defined in your TICK configuration, that you have
selected to be linked to.
- Files will be distributed using the TICK format software.
o Area prefix: ADS (Example ADSFIDO = ADS Networking Files)
8 characters maximum
[See example below.... refer to ADSFILES.lst for up to date list of
Official ADS File, this can be found on any ADS Site.
TAGNAME DESCRIPTION
------- -----------------------------
ADSFIDO Amiga Networking and Point Files
ADSGAMES Amiga Games
ADSINFO OFFICIAL ADS Information & News
ADSMISC Non-Developer Submitted Files
ADSMUSIC Amiga Music Scores, Sound Samples
ADSNETDV Network Developer Source/Docs
ADSSTMOD Sound Tracker Modules
ADSVIDEO Video Related files
Remember that these only exist in your tick.cfg file,
and are NOT message bases.
--------------------------------------------------------------
o Hatching Files
- Files may only be hatched into ADS by approved Hatching Sites.
- All File Hatchings must be accompanied by a long descriptions file
with the same name as the Program plus the extension of ADS in Ascii
format using CR+LF. i.e (Myfile-1.lzh + Myfile-1.ADS would be the two
files Hatched.) Announcement messages are encouraged to be posted in
the ADS echo tagname ADS_FILE_REL but is not mandatory.
o Posting the Software Announcement Message
- A Software Announcement message should include all necessary
information regarding the file hatched into ADS.
- Sample Message.
Subject: <filename>
Software Announcement!
============================================================
Filename:
ADS Area:
Filesize:
Origin:
[2-3 PARAGRAPH description of what this file does]
Author:
[Hatched on: DD - MMM - YY <date>]
============================================================
[end of suggested announcement format]
o Hatching template
ADS File Description Form
Revision 001 20-Nov-93
ADS format (c)Copyright 1990 - 1993 ADS International
ADS Sites to contact for Newest Revision Magic Name ADSHATCH.TMP.
------------------------------------------------------------------------------
1:120/229 - Don Plesky - Zone 1 Coordinator
ADSSTAR/Filebone Hatch Site
2:203/424 - Christian Carlsson - Zone 2 Coordinator
ADSSTAR
3:714/909 - Mario Nicotra - Zone 3 Coordinator
ADSSTAR
Notice to All: Authorized ADS Star's,Dhubs & Hatching Sites.
Effective: 18-Jan-93
ADS international will be making the following changes in its
Hatching of Files into the ADS Network.
o All Files that are to be Hatched into ADS International must be
Hatched with this Form and Authored Programs being Hatched Separately.
i.e, (Myfile-1.lzh, myfile-2.lzh myfile-3.lzh Myfile-1.ads).
The myfile-1.ads will contain this Form in Txt format which will
MUST be the same NAME as the FIRST File of a Set of Files if more then
one is Hatched. it will also Contain a detailed long description for
the program Myfile, along with the file archive names and sizes.
i.e, (Myfile-1.lzh 145432, Myfile-2.lzh 93148, Myfile-3.lzh 22314).
o Official Language. The official Language to be used for the
ECHOmail areas (ADS_ANNOUNCE, ADS_FIL_REL) *and* all files and
descriptions is ENGLISH. A program may have additional language
versions contained within the archive, but there MUST be an
English version.
o Filenames must not exceed 8 characters plus 3 characters for
an extension. Only one '.' may be used per filename. All non-
conforming filenames will be put on HOLD by the coordinator
pending response by the system entering such file into the
network.
*-Note Files in side the archive maybe in any lenth or format
the author so desires.
o To minimize storage space and online costs, as well as the
maintenance of a consistent storage format, all submissions
must be in the LHArc (-lh1- or -lh5-) format with the filename
consisting of an up to 8 character name, the character '.' and
the suffix(s):
.LZH for -lh1- archives
.LHA for -lh5- archives
o Archives larger than 600,000 bites must be broken down into
smaller archives. i.e. edit.lha with a file size of xxxxxxx
would be broken down into.
edit1.lha
edit2.lha
o Files will be distributed using the TICK format software.
(Amiga Software)
StarTick [v2.39] Chris Adams (1:308/80) --- Star-Net
MyTick [v2.05] Chris Adams (1:308/80) --- MEBBSNet
AmigaTick [v0.75] Russel Miranda --- Paragon
XTick [v0.61] Magnus Lilja --- XenoLink
FoozleTick [v0.92] --- generic
(MS-DOS Software)
TICK [v2.10] Barry Geller (1:266/12) --- IBM
o Regarding the .ADS file Hatchs this is what wilL Not be Acceptable:
What is shown below is a standard files listing
Area ADSMISC Programs
------------------------------------------------------------------------
AGATEST.LHA 17708 92-Dec-27 [777] AGAtest - Archive
AGATEST.ADS 218 92-Dec-27 [777] AGAtest - Description
This is the format WiLL NOT Used by ADS. The "[777] AGAtest - Archive"
doesn't give the user any clue at all what really is in this file...
(s)he has to view or download the .ADS file instead, which isn't that
hard for an on-line user sure, but what about those doing freqs?
Having to freq the .ADS files first is a real pain. ADS would get a lot
of complaints for file listings Not showing a Short Description of the
program file in the filelist.
Acceptable Hatchs would look like this..
Area ADSMisc Files
-----------------------------------------------------------------------
AGATEST.LHA 17708 92-Dec-27 [777] AGAtest - Shows all 2^24 colours
on AGA machines, includes source
AGATEST.ADS 218 92-Dec-27 [777] AGAtest - Detailed Description
Now, that does say a lot more, doesn't it?
o The Following Only Applies to Zone 1 at this time.
With the addition of the FileName.ADS it will no longer be mandatory
that a long description be posted in ADS_FILE_REL in Zone 1. Authors
are encouraged to post an Announcement in ADS_ANNOUNCE, which is
required to be carried by ALL ADS Sites. (This is Now Zone 1 Backbone
echo).
o The following applies Only to Zone's 2 & 3 this time.
NOTE: ALL sites carrying the ADS_FIL_REL echo are to make SURE
that it is READ-ONLY to those who do not Hatch files.
All software releases must have an accompanying message posted
into the ADS_FIL_REL echo, announcing it's availability. These
messages should take the following format:
o Posting the Software Announcement Message
Subject: <filename>
Software Announcement!
============================================================
Filename:
ADS Area:
Filesize:
Origin:
[2-3 PARAGRAPH description of what this file does]
Author:
[Hatched on: <date>]
============================================================
[end of suggested announcement format]
-------------------------------------------------------------------------------
o ADS Hatching Template, Note this template will be left in its original
form of CR+LF, if these files do Not contain CR+LFs, your files will
go no further the the first ADSSTAR.
o Template: Hatching.
Please make avail the form below to your authorized Hatching node/authors
so that they can fill out their portion of the file. Be sure, however to have
your section at the bottom filled out first, it not only lets us know who
hatched the file but also gives you an opportunity to advertise your system.
This file then is to be named filename.ADS and hatched right along with the
file it is describing. i.e. editor.lha, editor.ads being the hatch files.
* NOTICE * : If this file is not with its .lzh/lha counterpart and Not in CR+LF
format, then the file is NOT to be hatched into ADS until the author provides
you with it.
---------------------------Sysop Cut Here------------------------------------
(give to author)
ADS File Description Form
Revision 001 20-Nov-93
ADS format (c)Copyright 1990 - 1993 ADS International
Notice!! Authors: If this Form is not filled out in CR+LF format or not
sent in with your program, your program will NOT be hatched thru ADS
International.
For latest list of ADS SITES a file is obtainable under the name of
ADSSYSZx.LHA (x being the zone number).
Rename this Form to your File: Name.ADS.
Example: My program Name = Myterm.lzh
This File in Txt Format (Do Not Compress) = Myterm.ADS
Maximum of 80 lines with CR+LFs from beginning to end of file..
Do Not Change any INFO or the format of this form nor in the
Footer as, this is used by Authorized ADS Hatching Sites only.
Please feel free to post a message in the ADS Announcement & Chat Echo
about your Program that is about to be hatched.
-------------------------------------------------------------------------------
(give to author)
ADS File Description Form
Revision 001 20-Nov-93
ADS format (c)Copyright 1990 - 1993 ADS International
Notice!! Authors: If this Form is not filled out in CR+LF format or not
sent in with your program, your program will NOT be hatched thru ADS
International.
For latest list of ADS SITES a file is obtainable under the name of
ADSSYSZx.LHA (x being the zone number).
Rename this Form to your File: Name.ADS.
Example: My program Name = Myterm.lzh
This File in Txt Format (Do Not Compress) = Myterm.ADS
Maximun of 80 lines with CR+LFs from begining to end of file..
Do Not Change any INFO or the format of this form nor in the
Footer as, this is used by Authorized ADS Hatching Sites only.
Please feel free to post a message in the ADS Announcement & Chat Echo
about your Program that is about to be hatched.
-------------------------------------------------------------------------------
ADS File Description
--------------------
Program Name: Registration Fee:
Author:
Files / Size:(i.e)
MyFile-1.ads (Size Not Needed)
Myfile-1.lzh 145432
Myfile-2.lzh 93148
Myfile-3.lzh 22314)
Released:(i.e) 20-JAN-93)
=====================================================================
(Enter Program Name Here)
=====================================================================
Long Description:
============================================================================
Required Dos: 2.0 or later
Computer: All Amigas
Ram: 512k
Suggested Hardware: Hard drive
Other: Joy Stick
============================================================================
(Replace with your own System info (Authorized ADS Hatch Sites ONLY!) Do NOT
increase this section, however delete these 2 lines for more space)Example:
ADS Zone: Zone 1
ADS Hatch Site: Don Plesky
ADS Position: ADS Zone 1 Coordinator
BBS Name: EastPointe Amiga BBS
Phone Number(s): 810-773-6959
Network Address: FidoNet 1:120/229
Network Region: 11, USA
BBS Hours: 24hour
BBS Software: DLG
BBS Storage Space: 965 Megs
File Requestable : <y> Y < > N
File Request Hours : ____________________
_____________________________________________________________________________
ADS format (c)Copyright 1990 - 1993 ADS International
o Posting the Software Announcement Template.
Subject: <filename>
Software Announcement!
============================================================
Filename:
ADS Area:
Filesize:
Origin:
[2-3 PARAGRAPH description of what this file does]
Author:
[Hatched on: <date>]
============================================================
[end of suggested announcement format]
o Official Language. The official Language to be used for this Form
& ECHOmail areas *and* all file area descriptions is ENGLISH.
A program may have additional language versions contained within
the archive, but there MUST be an English version included.
o General rules for hatching files.
RULES and GUIDELINES
____________________________________________________________
1. NO COMMERCIAL PROGRAMS ALLOWED. Public Domain (PD)/Shareware/
Freeware only. Beta/Gamma/Full-release software will be
accepted into ADS. Version identifiers must be included in
either the filename or description or both.
2. Only defined ADS Stars DHubs or Authorized Nodes
can contribute files. (Authorized nodes will need the
permission of the Zone Co-ordinator or their DHub.
PRIOR to releasing files into the network.)
3. All file submissions to the ADS must be sent to one of
the following, an authorized ADS Zone Star, Star, DHub.
Any software developer interested in submitting their
program(s)/file(s) through ADS is strongly encouraged
to do so, *BUT* you must contact EITHER the ADS Zone Co-
ordinator OR your immediate upstream ADS DHub prior to release.
THE ADS ADMINISTRATION BOARD, ZONESTARS, STARS OR DHUBS WILL NOT BE
HELD RESPONSIBLE FOR ANY DAMAGES CAUSED BY ANY FILE SENT VIA ADS.
ADS WILL make every effort possible to prevent the distribution of
copyrighted commercial software/files. ADS will NOT be held responsible
for the mistaken distribution of any copyrighted software/files.
4. The decision to distribute any file is at the sole discretion
of the ADS Zone Stars an ADS Stars.
Disagreements should be submitted via Netmail to the ADS Zone 1
Coordinator.
5. Any downward link MUST be removed at the instruction of the
ADSSTAR/ADS Zone Coordinator. Current Fidonet Policy documents
will serve as a guideline to moderate the ADS_FIL_REL and
ADS_ANNOUNCE echos and all the current file echoes
(distribution echos).
6. All Stars, DHubs and Hatching Nodes MUST carry the ADS_FIL_REL echo.
Hatching Nodes will not be required to be linked into more than
ONE file distribution echo in order to qualify as an ADS hatching node.
A node may link to as many or as few File Echoes as they
choose, however the node is required to receive both ADS file
transfers and the ADS_FIL_REL from the same location. A node may
not receive ADS File Echos from more than one location.
8. Upward ADS links can only be established thru a ADSSTAR/ADSDHUB
with the approval of the Zone Coordinator.
Only the ADSSTAR(s), DHub(s) and approved developers may hatch
files into the ADS network.
9. Developers may gain blanket authorization (good for any
software they release) by submitting a letter for approval
from their ADS Zone Coordinator and a copy of the letter is
sent to their DHub. If you are denied, you may appeal by
sending a Netmail Message to the ADS Zone 1 Coordinator.
The Z1C would then bring it to the Administration board for
consideration. Their decision is final.
10. All ADS nodes are requested to display the letters "ADS"
(ADS) in their * Origin: lines so as to identify themselves
as an approved ADS site.
11. All files distributed via the ADS will have a descriptive
file Hatched with it. The descriptive file will contain the
filename with the ext of .ADS and Must be left in the template
format CR+LFs.
All files will be hatch using Tick compatible software, and will
contain a one line descriptive line no longer the 80 chars.
This file will have an extension of:
.TIC
Filenames must not exceed 8 characters plus 3 characters for
an extension. Only one '.' may be used per filename. All non-
conforming filenames will be put on HOLD by the coordinator
pending response by the system entering such file into the
network.
12. To minimize storage space and online costs, as well as the
maintenance of a consistent storage format, all submissions
must be in the LHArc (-lh1- or -lh5-) format with the filename
consisting of an up to 8 character name, the character '.' and
the suffix(s):
.LZH for -lh1- archives
.LHA for -lh5- archives
13. All links (both downlink and uplink) will be required to use
a password. Intention is to eliminate as many possibilities
of some 'unknown' node submitting a 'trojan horse' or an
unapproved file into the system.
14. Files received from any node other than from a ADS Zone-Star,
ADS Star or ADS DHub upwards, are not to be displayed as 'ADS Files'.
The only exception to this rule, would be ADS files received
directly from the Zone 1 FileBone.
15. Cost Recovery may be applied to the ADS network via a method of
Contributions. Where cost recovery is in force then all users of the
network shall contribute to its operation, and the operation is to
include the long distance cost of bring in the ADS Files and Echos only.
You can NOT charge for the basic service charge.
*-Note if a Node has implemented a cost recovery plan and it is found
out that this Node is making a profit (S)He will lose their ADS Status.
16. Any system operator or ADS recipient found willfully violating
the ADS rules and regulations can be subject to an ADS Feed
Disconnection. The relevant Zone coordinator and/or Star will determine
the severity of the breach and the disciplinary action taken.
17. This document can be changed at any time by the Administration Board
without prior warning. A message notifying all Dhubs/Stars/Zcs will
be posted in the ADS_COORD and ADS_STAR echoes.
------------------------------------------------------------
DISCLAIMER
____________________________________________________________
All brand and product names mentioned are trademarks or registered
trademarks of their respective companies/authors.
----- END OF POLICY ------